Systems and Methods for Performing Multi-Touch Operations on a Head-Mountable Device

ABSTRACT

Embodiments described herein may provide a configuration of input interfaces used to perform multi-touch operations. An example device may involve: (a) a housing arranged on a head-mountable device, (b) a first input interface arranged on either a superior or an inferior surface of the housing, (c) a second input interface arranged on a surface of the housing that is opposite to the first input interface, and (d) a control system configured to: (1) receive first input data from the first input interface, where the first input data corresponds to a first input action, and in response, cause a camera to perform a first operation in accordance with the first input action, and (2) receive second input data from the second input interface, where the second input data corresponds to a second input action(s) on the second input interface, and in response, cause the camera to perform a second operation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/084,674, filed on Nov. 20, 2013, and entitled “Systems and Methodsfor Performing Multi-Touch Operations on a Head-Mountable Device.” Thisapplication is also a continuation of international applicationPCT/US2014/063123, filed on Oct. 30, 2014, which claims benefit of U.S.patent application Ser. No. 14/084,674, both of which are hereinincorporated by reference as if fully set forth in this description.

BACKGROUND

Unless otherwise indicated herein, the materials described in thissection are not prior art to the claims in this application and are notadmitted to be prior art by inclusion in this section.

Computing devices such as personal computers, laptop computers, tabletcomputers, cellular phones, and countless types of Internet-capabledevices are increasingly prevalent in numerous aspects of modern life.Over time, the manner in which these devices are providing informationto users is becoming more intelligent, more efficient, more intuitive,and/or less obtrusive.

The trend toward miniaturization of computing hardware, peripherals, aswell as of sensors, detectors, and image and audio processors, amongother technologies, has helped open up a field sometimes referred to as“wearable computing.” In the area of image and visual processing andproduction, in particular, it has become possible to consider wearabledisplays that place a graphic display close enough to a wearer's (oruser's) eye(s) such that the displayed image appears as a normal-sizedimage, such as might be displayed on a traditional image display device.The relevant technology may be referred to as “near-eye displays.”

Wearable computing devices with near-eye displays may also be referredto as “head-mountable displays” (HMDs), “head-mounted displays,”“head-mounted devices,” or “head-mountable devices.” A head-mountabledisplay places a graphic display or displays close to one or both eyesof a wearer. To generate the images on a display, a computer processingsystem may be used. Such displays may occupy a wearer's entire field ofview, or only occupy part of wearer's field of view. Further,head-mounted displays may vary in size, taking a smaller form such as aglasses-style display or a larger form such as a helmet, for example.

Emerging and anticipated uses of wearable displays include applicationsin which users interact in real time with an augmented or virtualreality. Such applications can be mission-critical or safety-critical,such as in a public safety or aviation setting. The applications canalso be recreational, such as interactive gaming. Many otherapplications are also possible.

SUMMARY

Example embodiments may help to provide an ergonomic configuration ofinput interfaces in a computing device, such as a head-mountable device(HMD). In particular, a first input interface may be arranged on a top,a bottom, or a side surface of a housing that is attached to or part ofan HMD. A second input interface may be arranged on a surface of thehousing opposite to the first input interface. A control system may bein communication with the first and second input interfaces and mayreceive data from one or both of the interfaces corresponding to inputsat the interfaces. The control system may then cause a camera of the HMDto perform one or more operations in response to the received data.

In one aspect, a device may include: (a) a head-mountable frameincluding a housing arranged on at least one side arm, (b) a first inputinterface arranged on either a superior surface or an inferior surfaceof the housing, (c) a second input interface arranged on a surface ofthe housing that is opposite to the first input interface, and (d) acontrol system configured to: (1) receive first input data from thefirst input interface, where the first input data corresponds to a firstinput action, and responsive to the receipt of the first input data,cause a camera of the device to perform a first camera operation inaccordance with the first input action, and (2) receive second inputdata from the second input interface, where the second input datacorresponds to one or more second input actions on the second inputinterface, and responsive to the receipt of the second input data, causethe camera to perform a second camera operation that is different fromthe first camera operation.

In another aspect, a method may involve: (a) receiving first input datafrom a first input interface that corresponds to a first input action,where the first input interface is arranged on either a superior surfaceor an inferior surface of a housing, and where the housing is arrangedon at least one side arm of a head-mountable frame of a device, (b)responsive to the receipt of the first input data, causing a camera ofthe device to perform a first camera operation in accordance with thefirst input action, (c) receiving second input data from a second inputinterface that corresponds to a second input action, where the secondinput interface is arranged on a surface of the housing that is oppositeto the first input interface, and (d) responsive to the receipt of thesecond input data, causing the camera to perform a second cameraoperation that is different from the first camera operation.

In another aspect, a non-transitory computer readable medium has storedtherein instructions executable by a computing device to cause thecomputing device to perform functions comprising: (a) receiving firstinput data from a first input interface that corresponds to a firstinput action, where the first input interface is arranged on either asuperior surface or an inferior surface of a housing, and where thehousing is arranged on at least one side arm of a head-mountable frameof a device, (b) responsive to the receipt of the first input data,causing a camera of the device to perform a first camera operation inaccordance with the first input action, (c) receiving second input datafrom a second input interface that corresponds to a second input action,where the second input interface is arranged on a surface of the housingthat is opposite to the first input interface, and (d) responsive to thereceipt of the second input data, causing the camera to perform a secondcamera operation that is different from the first camera operation.

In a further aspect, a system may include: (a) means for receiving firstinput data from a first input interface that corresponds to a firstinput action, wherein the first input interface is arranged on either asuperior surface or an inferior surface of a housing, and wherein thehousing is arranged on at least one side arm of a head-mountable frameof a device, (b) means for, responsive to the receipt of the first inputdata, causing a camera of the device to perform a first camera operationin accordance with the first input action, (c) means for receivingsecond input data from a second input interface that corresponds to asecond input action, wherein the second input interface is arranged on asurface of the housing that is opposite to the first input interface,and (d) means for, responsive to the receipt of the second input data,causing the camera to perform a second camera operation that isdifferent from the first camera operation.

These as well as other aspects, advantages, and alternatives will becomeapparent to those of ordinary skill in the art by reading the followingdetailed description, with reference where appropriate to theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates a wearable computing system according to an exampleembodiment.

FIG. 1B illustrates an alternate view of the wearable computing deviceillustrated in FIG. 1A.

FIG. 1C illustrates another wearable computing system according to anexample embodiment.

FIG. 1D illustrates another wearable computing system according to anexample embodiment.

FIGS. 1E to 1G are simplified illustrations of the wearable computingsystem shown in FIG. 1D, being worn by a wearer.

FIG. 2 is a simplified block diagram of a computing device according toan example embodiment.

FIG. 3A illustrates an example housing configuration according to anexample embodiment.

FIG. 3B illustrates another example housing configuration according toan example embodiment.

FIG. 4 is a flow chart illustrating a method according to an exampleembodiment.

FIG. 5A illustrates a first example use of an example housing, inaccordance with an embodiment.

FIG. 5B illustrates a second example use of an example housing, inaccordance with an embodiment.

FIG. 5C illustrates a third example use of an example housing, inaccordance with an embodiment.

FIG. 6A illustrates a first example camera preview corresponding to useof the example housing as shown in FIG. 5A, in accordance with anembodiment.

FIG. 6B illustrates a second example camera preview corresponding to useof the example housing as shown in FIG. 5B, in accordance with anembodiment.

FIG. 6C illustrates a third example camera preview corresponding to useof the example housing as shown in FIG. 5C, in accordance with anembodiment.

DETAILED DESCRIPTION

Example methods and systems are described herein. It should beunderstood that the words “example” and “exemplary” are used herein tomean “serving as an example, instance, or illustration.” Any embodimentor feature described herein as being an “example” or “exemplary” is notnecessarily to be construed as preferred or advantageous over otherembodiments or features. In the following detailed description,reference is made to the accompanying figures, which form a partthereof. In the figures, similar symbols typically identify similarcomponents, unless context dictates otherwise. Other embodiments may beutilized, and other changes may be made, without departing from thespirit or scope of the subject matter presented herein.

The example embodiments described herein are not meant to be limiting.It will be readily understood that the aspects of the presentdisclosure, as generally described herein, and illustrated in thefigures, can be arranged, substituted, combined, separated, and designedin a wide variety of different configurations, all of which arecontemplated herein.

I. OVERVIEW

One or more input interfaces can be found on a variety of computingdevices, including HMD's (head-mountable devices). Typically, an inputinterface may be configured to detect a limited set of inputs based, inpart, on where the input interface is arranged on a computing device. Insome applications, it may be useful to arrange multiple input interfacesin an ergonomic manner to allow a user to perform operations thatotherwise may be difficult to perform in a different arrangement.

Example embodiments may provide for multiple input interfaces arrangedon a housing that is arranged on an HMD. The multiple input interfacesmay be arranged in a number of ergonomic configurations that could helpa user to conveniently operate the HMD. In some embodiments, a firstinput interface may be arranged on a first surface of the housing, andthe second input interface may be arranged on a second surface of thehousing, which is opposite to the first surface. The first surface maybe a top, a bottom or a first side surface, and the second surface maybe the bottom, the top, or a second side surface, among otherpossibilities.

The input interfaces may be one of or a combination of several types ofinput interfaces, such as finger operable touch sensors. The inputinterfaces may detect input actions and transmit data to a controlsystem of the HMD in response to the detected input actions. The controlsystem may then perform a number of operations in response to thereceived data.

In example embodiments, the input interfaces may receive a series ofinput actions and accordingly, transmit a series of data to the controlsystem. In turn, the control system may cause a camera of the device toperform a first camera operation (e.g., zoom the camera, focus thecamera, adjust a camera setting, etc.) in accordance with at least oneof the input actions and then cause the camera to perform a secondcamera operation different from the first camera operation in responseto another input action.

As such, the configuration of input interfaces may provide the user withergonomic benefits for performing a camera operation, among otherexample operations. In some embodiments, where the first input interfaceis arranged on the bottom surface and the second input interface isarranged on the top surface, when the user positions the user's thumb onthe first input interface for one control, the user's middle and pointerfingers may naturally rest on the top surface where the second inputinterface is arranged. When the user uses both the first and secondinput interfaces at once, the user may feel as though the user isnaturally squeezing the housing, such that the thumb opposes thepointer/middle finger. This accordingly may provide the user withgreater control and/or more fine-tuned control of the HMD.

Other applications of the example embodiments described herein arepossible. For instance, an ergonomic configuration of input interfacesmay be used to initiate and adjust volume control of a speaker. In otherinstances, an ergonomic configuration of input interfaces may be used tocontrol an audio player (e.g., select, play, pause, or skip a song).Other applications are also possible.

It should be understood that the above embodiments and others describedherein are provided for purposes of illustration, and are not intendedto be limiting. Variations on the above embodiments and otherembodiments are possible, without departing from the scope of theinvention as set forth by the claims.

II. EXAMPLE WEARABLE COMPUTING DEVICES

Systems and devices in which example embodiments may be implemented willnow be described in greater detail. In general, an example system may beimplemented in or may take the form of a wearable computer (alsoreferred to as a wearable computing device). In an example embodiment, awearable computer takes the form of or includes a head-mountable device(HMD).

An example system may also be implemented in or take the form of otherdevices, such as a mobile phone, among other possibilities. Further, anexample system may take the form of non-transitory computer readablemedium, which has program instructions stored thereon that areexecutable by a processor to provide the functionality described herein.An example system may also take the form of a device such as a wearablecomputer or mobile phone, or a subsystem of such a device, whichincludes such a non-transitory computer readable medium having suchprogram instructions stored thereon.

An HMD may generally be any display device that is capable of being wornon the head and places a display in front of one or both eyes of thewearer. An HMD may take various forms such as a helmet or eyeglasses. Assuch, references to “eyeglasses” or a “glasses-style” HMD should beunderstood to refer to an HMD that has a glasses-like frame so that itcan be worn on the head. Further, example embodiments may be implementedby or in association with an HMD with a single display or with twodisplays, which may be referred to as a “monocular” HMD or a “binocular”HMD, respectively.

FIG. 1A illustrates a wearable computing system according to an exampleembodiment. In FIG. 1A, the wearable computing system takes the form ofa head-mountable device (HMD) 102 (which may also be referred to as ahead-mounted display). It should be understood, however, that examplesystems and devices may take the form of or be implemented within or inassociation with other types of devices, without departing from thescope of the invention. As illustrated in FIG. 1A, the HMD 102 includesframe elements including lens-frames 104, 106 and a center frame support108, lens elements 110, 112, and extending side-arms 114, 116. Thecenter frame support 108 and the extending side-arms 114, 116 areconfigured to secure the HMD 102 to a user's face via a user's nose andears, respectively.

Each of the frame elements 104, 106, and 108 and the extending side-arms114, 116 may be formed of a solid structure of plastic and/or metal, ormay be formed of a hollow structure of similar material so as to allowwiring and component interconnects to be internally routed through theHMD 102. Other materials may be possible as well.

One or more of each of the lens elements 110, 112 may be formed of anymaterial that can suitably display a projected image or graphic. Each ofthe lens elements 110, 112 may also be sufficiently transparent to allowa user to see through the lens element. Combining these two features ofthe lens elements may facilitate an augmented reality or heads-updisplay where the projected image or graphic is superimposed over areal-world view as perceived by the user through the lens elements.

The extending side-arms 114, 116 may each be projections that extendaway from the lens-frames 104, 106, respectively, and may be positionedbehind a user's ears to secure the HMD 102 to the user. The extendingside-arms 114, 116 may further secure the HMD 102 to the user byextending around a rear portion of the user's head. Additionally oralternatively, for example, the HMD 102 may connect to or be affixedwithin a head-mounted helmet structure. Other configurations for an HMDare also possible.

The HMD 102 may also include an on-board computing system 118, an imagecapture device 120, a sensor 122, and a finger-operable touch pad 124.The on-board computing system 118 is shown to be positioned on theextending side-arm 114 of the HMD 102; however, the on-board computingsystem 118 may be provided on other parts of the HMD 102 or may bepositioned remote from the HMD 102 (e.g., the on-board computing system118 could be wire- or wirelessly-connected to the HMD 102). The on-boardcomputing system 118 may include a processor and memory, for example.The on-board computing system 118 may be configured to receive andanalyze data from the image capture device 120 and the finger-operabletouch pad 124 (and possibly from other sensory devices, user interfaces,or both) and generate images for output by the lens elements 110 and112.

The image capture device 120 may be, for example, a camera that isconfigured to capture still images and/or to capture video. In theillustrated configuration, image capture device 120 is positioned on theextending side-arm 114 of the HMD 102; however, the image capture device120 may be provided on other parts of the HMD 102. The image capturedevice 120 may be configured to capture images at various resolutions orat different frame rates. Many image capture devices with a smallform-factor, such as the cameras used in mobile phones or webcams, forexample, may be incorporated into an example of the HMD 102.

Further, although FIG. 1A illustrates one image capture device 120, moreimage capture device may be used, and each may be configured to capturethe same view, or to capture different views. For example, the imagecapture device 120 may be forward facing to capture at least a portionof the real-world view perceived by the user. This forward facing imagecaptured by the image capture device 120 may then be used to generate anaugmented reality where computer generated images appear to interactwith or overlay the real-world view perceived by the user.

The sensor 122 is shown on the extending side-arm 116 of the HMD 102;however, the sensor 122 may be positioned on other parts of the HMD 102.For illustrative purposes, only one sensor 122 is shown. However, in anexample embodiment, the HMD 102 may include multiple sensors. Forexample, an HMD 102 may include sensors 102 such as one or moregyroscopes, one or more accelerometers, one or more magnetometers, oneor more light sensors, one or more infrared sensors, and/or one or moremicrophones. Other sensing devices may be included in addition or in thealternative to the sensors that are specifically identified herein.

The finger-operable touch pad 124 is shown on the extending side-arm 114of the HMD 102. However, the finger-operable touch pad 124 may bepositioned on other parts of the HMD 102. Also, more than onefinger-operable touch pad may be present on the HMD 102. Thefinger-operable touch pad 124 may be used by a user to input commands.The finger-operable touch pad 124 may sense at least one of a pressure,position and/or a movement of one or more fingers via capacitivesensing, resistance sensing, or a surface acoustic wave process, amongother possibilities. The finger-operable touch pad 124 may be capable ofsensing movement of one or more fingers simultaneously, in addition tosensing movement in a direction parallel or planar to the pad surface,in a direction normal to the pad surface, or both, and may also becapable of sensing a level of pressure applied to the touch pad surface.In some embodiments, the finger-operable touch pad 124 may be formed ofone or more translucent or transparent insulating layers and one or moretranslucent or transparent conducting layers. Edges of thefinger-operable touch pad 124 may be formed to have a raised, indented,or roughened surface, so as to provide tactile feedback to a user whenthe user's finger reaches the edge, or other area, of thefinger-operable touch pad 124. If more than one finger-operable touchpad is present, each finger-operable touch pad may be operatedindependently, and may provide a different function.

In a further aspect, HMD 102 may be configured to receive user input invarious ways, in addition or in the alternative to user input receivedvia finger-operable touch pad 124. For example, on-board computingsystem 118 may implement a speech-to-text process and utilize a syntaxthat maps certain spoken commands to certain actions. In addition, HMD102 may include one or more microphones via which a wearer's speech maybe captured. Configured as such, HMD 102 may be operable to detectspoken commands and carry out various computing functions thatcorrespond to the spoken commands.

As another example, HMD 102 may interpret certain head-movements as userinput. For example, when HMD 102 is worn, HMD 102 may use one or moregyroscopes and/or one or more accelerometers to detect head movement.The HMD 102 may then interpret certain head-movements as being userinput, such as nodding, or looking up, down, left, or right. An HMD 102could also pan or scroll through graphics in a display according tomovement. Other types of actions may also be mapped to head movement.

As yet another example, HMD 102 may interpret certain gestures (e.g., bya wearer's hand or hands) as user input. For example, HMD 102 maycapture hand movements by analyzing image data from image capture device120, and initiate actions that are defined as corresponding to certainhand movements.

As a further example, HMD 102 may interpret eye movement as user input.In particular, HMD 102 may include one or more inward-facing imagecapture devices and/or one or more other inward-facing sensors (notshown) that may be used to sense a user's eye movements and/orpositioning. As such, certain eye movements may be mapped to certainactions. For example, certain actions may be defined as corresponding tomovement of the eye in a certain direction, a blink, and/or a wink,among other possibilities.

HMD 102 also includes a speaker 125 for generating audio output. In oneexample, the speaker could be in the form of a bone conduction speaker,also referred to as a bone conduction transducer (BCT). Speaker 125 maybe, for example, a vibration transducer or an electroacoustic transducerthat produces sound in response to an electrical audio signal input. Theframe of HMD 102 may be designed such that when a user wears HMD 102,the speaker 125 contacts the wearer. Alternatively, speaker 125 may beembedded within the frame of HMD 102 and positioned such that, when theHMD 102 is worn, speaker 125 vibrates a portion of the frame thatcontacts the wearer. In either case, HMD 102 may be configured to sendan audio signal to speaker 125, so that vibration of the speaker may bedirectly or indirectly transferred to the bone structure of the wearer.When the vibrations travel through the bone structure to the bones inthe middle ear of the wearer, the wearer can interpret the vibrationsprovided by BCT 125 as sounds.

Various types of bone-conduction transducers (BCTs) may be implemented,depending upon the particular implementation. Generally, any componentthat is arranged to vibrate the HMD 102 may be incorporated as avibration transducer. Yet further it should be understood that an HMD102 may include a single speaker 125 or multiple speakers. In addition,the location(s) of speaker(s) on the HMD may vary, depending upon theimplementation. For example, a speaker may be located proximate to awearer's temple (as shown), behind the wearer's ear, proximate to thewearer's nose, and/or at any other location where the speaker 125 canvibrate the wearer's bone structure.

FIG. 1B illustrates an alternate view of the wearable computing deviceillustrated in FIG. 1A. As shown in FIG. 1B, the lens elements 110, 112may act as display elements. The HMD 102 may include a first projector128 coupled to an inside surface of the extending side-arm 116 andconfigured to project a display 130 onto an inside surface of the lenselement 112. Additionally or alternatively, a second projector 132 maybe coupled to an inside surface of the extending side-arm 114 andconfigured to project a display 134 onto an inside surface of the lenselement 110.

The lens elements 110, 112 may act as a combiner in a light projectionsystem and may include a coating that reflects the light projected ontothem from the projectors 128, 132. In some embodiments, a reflectivecoating may not be used (e.g., when the projectors 128, 132 are scanninglaser devices).

In alternative embodiments, other types of display elements may also beused. For example, the lens elements 110, 112 themselves may include: atransparent or semi-transparent matrix display, such as anelectroluminescent display or a liquid crystal display, one or morewaveguides for delivering an image to the user's eyes, or other opticalelements capable of delivering an in focus near-to-eye image to theuser. A corresponding display driver may be disposed within the frameelements 104, 106 for driving such a matrix display. Alternatively oradditionally, a laser or LED source and scanning system could be used todraw a raster display directly onto the retina of one or more of theuser's eyes. Other possibilities exist as well.

FIG. 1C illustrates another wearable computing system according to anexample embodiment, which takes the form of an HMD 152. The HMD 152 mayinclude frame elements and side-arms such as those described withrespect to FIGS. 1A and 1B. The HMD 152 may additionally include anon-board computing system 154 and an image capture device 156, such asthose described with respect to FIGS. 1A and 1B. The image capturedevice 156 is shown mounted on a frame of the HMD 152. However, theimage capture device 156 may be mounted at other positions as well.

As shown in FIG. 1C, the HMD 152 may include a single display 158 whichmay be coupled to the device. The display 158 may be formed on one ofthe lens elements of the HMD 152, such as a lens element described withrespect to FIGS. 1A and 1B, and may be configured to overlaycomputer-generated graphics in the user's view of the physical world.The display 158 is shown to be provided in a center of a lens of the HMD152, however, the display 158 may be provided in other positions, suchas for example towards either the upper or lower portions of thewearer's field of view. The display 158 is controllable via thecomputing system 154 that is coupled to the display 158 via an opticalwaveguide 160.

FIG. 1D illustrates another wearable computing system according to anexample embodiment, which takes the form of a monocular HMD 172. The HMD172 may include side-arms 173, a center frame support 174, and a bridgeportion with nosepiece 175. In the example shown in FIG. 1D, the centerframe support 174 connects the side-arms 173. The HMD 172 does notinclude lens-frames containing lens elements. The HMD 172 mayadditionally include a component housing 176, which may include anon-board computing system (not shown), an image capture device 178, anda button 179 for operating the image capture device 178 (and/or usablefor other purposes). Component housing 176 may also include otherelectrical components and/or may be electrically connected to electricalcomponents at other locations within or on the HMD. HMD 172 alsoincludes a BCT 186.

The HMD 172 may include a single display 180, which may be coupled toone of the side-arms 173 via the component housing 176. In an exampleembodiment, the display 180 may be a see-through display, which is madeof glass and/or another transparent or translucent material, such thatthe wearer can see their environment through the display 180. Further,the component housing 176 may include the light sources (not shown) forthe display 180 and/or optical elements (not shown) to direct light fromthe light sources to the display 180. As such, display 180 may includeoptical features that direct light that is generated by such lightsources towards the wearer's eye, when HMD 172 is being worn.

In a further aspect, HMD 172 may include a sliding feature 184, whichmay be used to adjust the length of the side-arms 173. Thus, slidingfeature 184 may be used to adjust the fit of HMD 172. Further, an HMDmay include other features that allow a wearer to adjust the fit of theHMD, without departing from the scope of the invention.

FIGS. 1E to 1G are simplified illustrations of the HMD 172 shown in FIG.1D, being worn by a wearer 190. As shown in FIG. 1F, when HMD 172 isworn, BCT 186 is arranged such that when HMD 172 is worn, BCT 186 islocated behind the wearer's ear. As such, BCT 186 is not visible fromthe perspective shown in FIG. 1E.

In the illustrated example, the display 180 may be arranged such thatwhen HMD 172 is worn, display 180 is positioned in front of or proximateto a user's eye when the HMD 172 is worn by a user. For example, display180 may be positioned below the center frame support and above thecenter of the wearer's eye, as shown in FIG. 1E. Further, in theillustrated configuration, display 180 may be offset from the center ofthe wearer's eye (e.g., so that the center of display 180 is positionedto the right and above of the center of the wearer's eye, from thewearer's perspective).

Configured as shown in FIGS. 1E to 1G, display 180 may be located in theperiphery of the field of view of the wearer 190, when HMD 172 is worn.Thus, as shown by FIG. 1F, when the wearer 190 looks forward, the wearer190 may see the display 180 with their peripheral vision. As a result,display 180 may be outside the central portion of the wearer's field ofview when their eye is facing forward, as it commonly is for manyday-to-day activities. Such positioning can facilitate unobstructedeye-to-eye conversations with others, as well as generally providingunobstructed viewing and perception of the world within the centralportion of the wearer's field of view. Further, when the display 180 islocated as shown, the wearer 190 may view the display 180 by, e.g.,looking up with their eyes only (possibly without moving their head).This is illustrated as shown in FIG. 1G, where the wearer has movedtheir eyes to look up and align their line of sight with display 180. Awearer might also use the display by tilting their head down andaligning their eye with the display 180.

FIG. 2 is a simplified block diagram of a computing device 210 accordingto an example embodiment. In an example embodiment, device 210communicates using a communication link 220 (e.g., a wired or wirelessconnection) to a remote device 230. The device 210 may be any type ofdevice that can receive data and display information corresponding to orassociated with the data. For example, the device 210 may be a heads-updisplay system, such as the head-mounted devices 102, 152, or 172described with reference to FIGS. 1A to 1G.

Thus, the device 210 may include a display system 212 comprising aprocessor 214 and a display 216. The display 210 may be, for example, anoptical see-through display, an optical see-around display, or a videosee-through display. The processor 214 may receive data from the remotedevice 230, and configure the data for display on the display 216. Theprocessor 214 may be any type of processor, such as a micro-processor ora digital signal processor, for example.

The device 210 may further include on-board data storage, such as memory218 coupled to the processor 214. The memory 218 may store software thatcan be accessed and executed by the processor 214, for example.

The remote device 230 may be any type of computing device or transmitterincluding a laptop computer, a mobile telephone, or tablet computingdevice, etc., that is configured to transmit data to the device 210. Theremote device 230 and the device 210 may contain hardware to enable thecommunication link 220, such as processors, transmitters, receivers,antennas, etc.

Further, remote device 230 may take the form of or be implemented in acomputing system that is in communication with and configured to performfunctions on behalf of client device, such as computing device 210. Sucha remote device 230 may receive data from another computing device 210(e.g., an HMD 102, 152, or 172 or a mobile phone), perform certainprocessing functions on behalf of the device 210, and then send theresulting data back to device 210. This functionality may be referred toas “cloud” computing.

In FIG. 2, the communication link 220 is illustrated as a wirelessconnection; however, wired connections may also be used. For example,the communication link 220 may be a wired serial bus such as a universalserial bus or a parallel bus. A wired connection may be a proprietaryconnection as well. The communication link 220 may also be a wirelessconnection using, e.g., Bluetooth® radio technology, communicationprotocols described in IEEE 802.11 (including any IEEE 802.11revisions), Cellular technology (such as GSM, CDMA, UMTS, EV-DO, WiMAX,or LTE), or Zigbee® technology, among other possibilities. The remotedevice 230 may be accessible via the Internet and may include acomputing cluster associated with a particular web service (e.g.,social-networking, photo sharing, address book, etc.).

II. EXAMPLE HARDWARE CONFIGURATIONS

An HMD, such as the head-mountable devices 102, 152, or 172, may includea housing (e.g., the component housing 176) that provides one or moreinput interfaces. The housing may be attached to a side arm of thehead-mounted device or the housing may be part of the side arm itself,e.g., the housing may form a segment of, or otherwise be arranged on,the side arm. In other examples, the housing may be arranged on anysuitable portion of a head-mountable frame of the head-mountable device,e.g., on any suitable portion of HMD 172 of FIG. 1D, among otherpossibilities.

The one or more input interfaces may be configured to receive userinputs and send data to a control system of the head-mountable deviceconnected to the one or more input interfaces in response to receivingthe user inputs. The control system (e.g., the on-board computing system118) may be configured to receive the data and cause the performance ofan operation in response to the data.

An input interface may be a mechanical button that can be physicallydepressed (e.g., button 179 in FIG. 1D), a touch sensor, a rocker, adial, a slider, a switch, or a wheel, among other input interfaces. Insome instances, the input interface may include multiple buttons, touchsensors, rockers, dials, sliders, or wheels, or the input interface mayinclude any combination thereof. The touch sensor may be afinger-operable touch pad (e.g., the finger-operable touch pad 124), asingle point touch sensor, or a touch sensor configured to detect a“floating touch.” A finger-operable touch pad may be configured toreceive finger gestures (example finger gestures are described below).In other instances, the touch sensor may be a multi-state touch sensor.For example, the touch sensor may be a three-state sensor whose statesinclude a normal state, a hover state, and a click state. The normalstate may indicate that the touch sensor is not currently touched, thehover state may indicate that a finger is hovering (or “floating”) abovethe touch sensor but not touching the touch sensor, and the click statemay indicate that the touch sensor is currently being touched. Otherexample multi-state sensors are also possible.

The one or more input interfaces may be arranged on the housing in anumber of different configurations. FIGS. 3A and 3B illustratesimplified examples of housing configurations containing multiple inputinterfaces according to example embodiments. FIGS. 3A and 3B illustratea housing which is formed by the union of a superior surface 310, aninferior surface 312, an anterior surface 314, a posterior surface 316and two side surfaces. The housing may be attached to or otherwise apart of the HMD such that the anterior surface 314 faces the front ofthe HMD (e.g., the anterior surface 314 may face in the direction of theline of sight of a wearer of the HMD), and the posterior surface 316faces the back of the HMD (e.g., the posterior surface 316 may facetowards the back of the head of a wearer of the HMD). The housing mayinclude a first input interface 330 and a second input interface 320.The first input interface 330 may include an anterior end 334 and aposterior end 336.

In example configuration 300, as shown in FIG. 3A, the second inputinterface 320 may be arranged on the superior surface 310, and the firstinput interface 330 may be arranged on the inferior surface 312. Inexample configuration 350, as shown in FIG. 3B, the second inputinterface 320 may be arranged on the inferior surface 312, and the firstinput interface 330 may be arranged on the superior surface 310.Notably, as shown in FIGS. 3A and 3B, the first input interface and thesecond input interface may be arranged opposite to each other to allow auser to conveniently perform otherwise cumbersome operations on the HMD.That is, the first input interface and the second input interface may bearranged in an ergonomic manner such that a user may perform a thumbgesture at the inferior surface 312, while the user performs anothergesture with a remaining finger at the superior surface 310. Otherconfigurations are also possible. For example, the first input interface330 may be arranged on a first side surface and the second inputinterface 320 may be arranged on a second side surface that is oppositethe first side surface.

In example embodiments, at least one of the input interfaces may beconfigured to detect finger gestures and transmit data indicating afinger gesture to the control system. The control system may beconfigured to perform an operation based on the finger gesture. Forexample, the control system may be configured to perform a cameraoperation, a volume operation, or an audio player operation, among otheroperations, in response to a finger gesture.

Generally, a camera operation may involve an adjustment, modification,or selection of one or more camera parameters. For example, a cameraoperation may involve zooming the camera, adjusting exposure levels,adjusting focus depth, adjusting white balance settings, switchingbetween filters (e.g., a black and white filter, a low-fidelity filter,an early bird filter, a toy camera filter, etc.), switching betweenstabilization modes, selecting a camera function, or generallynavigating camera settings, among other camera operations. It should beunderstood that a camera operation may involve the performance of one ofthe above discussed operations while the camera captures video.

A finger gesture may include a finger roll, a finger rub, or a fingerswipe, among other finger gestures. The finger gestures will beexplained with reference to the first input interface 330 and in thecontext of a camera operation of zooming a camera. It should beunderstood that this is for purposes of example and explanation only,and that the described finger gestures may be performed at any othersuitable input interface and may cause any of the above mentioned cameraoperations to occur.

A finger roll may involve rocking a finger back and forth on the firstinput interface 330 (e.g., in motion similar to a rocking chair). Forinstance, a finger may begin at the posterior end 336 and roll forwardtoward the anterior end 334. The control system may be configured tocause a camera to zoom in on an object (or cause a speaker's volumelevel to increase) in response to such a gesture. A finger roll maybegin at the anterior end 334 and roll backward toward the posterior end336. The control system may be configured to cause a camera to zoom out(or cause a volume level to decrease).

Similarly, a finger rub may involve rubbing (or otherwise sliding) afinger on the first input interface 330 forward or backward. The controlsystem may be configured to cause a camera to zoom in, in response to aforward finger rub (toward the anterior end 334). While the controlsystem may be configured to cause a camera to zoom out, in response to abackward finger rub (toward the posterior end 336).

Further, a finger swipe may involve a brief swipe of a finger on thefirst input interface 330 forward or backward, e.g., a finger swipe maybe a quick finger motion compared to a finger rub. The control systemmay be configured to cause a camera to zoom out, in response to aforward finger swipe (toward the anterior end 334), and cause the camerato zoom in, in response to a backward finger swipe (toward the posteriorend 336).

It should be understood that a forward finger gesture need not begin atthe posterior end 336 or a backward finger gesture need not begin at theanterior end 334. Generally, a forward finger gesture is a fingermovement that is in the direction towards the anterior end 334, while abackward finger gesture is a finger gesture that is in the directiontowards the posterior end 336, regardless of the starting point.

Other finger gestures are also possible. For example, the first inputinterface 330 may be configured to detect a finger pinch, e.g., aninward pinch or an outward pinch. In another example, the first inputinterface 330 may be configured to detect a prolonged touch, and thecontrol system may be configured to cause the camera to zoom in or out,if the prolonged touch is detected for more than a predefined amount oftime.

III. EXAMPLE METHODS

FIG. 4 is a flow chart illustrating a method 400, according to anexample embodiment. Illustrative methods, such as method 400, may becarried out in whole or in part by an HMD, such as the head-mountabledevices shown in FIGS. 1A to 1G. The method 400 may be carried out bycomponents of an HMD, such as a control system. Such a control systemmay include, for example, a processor and program instructions stored ona non-transitory computer-readable medium. However, an HMD's controlsystem may additionally or alternatively include other components.Further, an example method or portions thereof may be carried out bycomponents of an HMD other than a control system. Yet further, anexample method, or portions thereof, may be carried out by a computingdevice that is in communication with an HMD. An example method may alsobe carried out by other types of computing devices and/or combinationsof computing devices, without departing from the scope of the invention.Other examples of such computing devices include, but are not limitedto, other types of wearable computing devices, mobile phones, and tabletcomputers.

For purposes of example and explanation, the method 400 will bedescribed with reference to FIGS. 5A-5C, and FIGS. 6A-6C. FIGS. 5A-5Cillustrate example uses of an example housing of an HMD at variouspoints in time. FIGS. 6A-6C illustrate example camera previewscorresponding to the example uses as shown in FIGS. 5A-5C. It should beunderstood that method 400 is described with reference to FIGS. 5A-5Cand FIGS. 6A-6C for purposes of example and explanation only and shouldnot be construed to be limiting.

In example embodiments, the method 400 may begin at block 402 with thecontrol system receiving preliminary data from either a first inputinterface or a second input interface. At block 404, the control system,responsive to the receipt of the preliminary data, initiates a camera.At block 406, the control system receives first input data from thefirst input interface that corresponds to a first input action. At block408, the control system, responsive to the receipt of the first inputdata, causes the camera to perform a first camera operation inaccordance with the first input action. At block 410, the control systemreceives second input data from a second input interface thatcorresponds to a second input action. At block 412, the control system,responsive to the receipt of the second input data, causes the camera toperform a second camera operation that is different from the firstcamera operation. In other embodiments, the method 400 may begin atblock 406. That is, the control system may already be in a “camera mode”and thus, blocks 402 and 404 may not be necessary (as indicated by thedotted lines in FIG. 4). Each of the blocks shown with respect to FIG. 4is discussed further below.

a. Receiving Input Data Corresponding to a Preliminary Input Action

The example method 400 beings at block 402 with receiving preliminarydata from one of a first input interface and a second input interfacethat corresponds to a preliminary input action. The first inputinterface may be the first input interface 330 as described withreference to FIGS. 3A and 3B where the first input interface 330 may bearranged on either the superior surface 310 or the inferior surface 312of the housing. The second input interface may be the second inputinterface 320 where the second input interface 320 is arranged on asurface of the housing that is opposite to the first input interface330. For purposes of example and explanation, the method 400 will bedescribed with reference to the housing configuration 300 of FIG. 3A. Asdescribed above, the housing may be arranged on at least one side arm ofa head-mountable frame of the HMD

The preliminary input action may take the form of any suitable action ateither the first input interface or the second input interface, whichmay depend on the input interface type. For example, the preliminaryinput action may involve a click or depression of a button, a touch of atouch sensor, a finger hover above a touch sensor, a rocking of arocker, a turn of a dial, a slide of a slider, a flip of switch, or aspin of a wheel. In other instances, where the input interface is atouch sensor, the preliminary input action may involve a user pressing afinger to the touch sensor and holding the finger for a predefinedperiod of time, or the preliminary input action may involve one of thefinger gestures as described above. Other preliminary input actions arealso possible. In response to receiving a preliminary input action, thefirst input interface and the second input interface may be configuredto transmit the preliminary data to the control system.

In one example, the preliminary input action may be a touch input at thefirst input interface. With reference to FIG. 5A, which illustrates anexample use of the housing configuration 300 at a first point in time,such a touch input may be performed by a thumb 510 of a user's hand 500.As shown in FIG. 5A, the first input interface 330 may receive a touchinput 515 from the thumb 510. The touch input 515 may be a prolongedtouch (e.g., for 2 or more seconds) or a brief touch at the first inputinterface 330, among other touch input examples. The first inputinterface 330 may be configured to generate data in response todetecting the touch input 515 and transmit the data to the controlsystem of the HMD.

In other embodiments, the preliminary input action may involve an inputaction at the second input interface. For example, the preliminary inputaction may involve a user pressing down on the second input interface,which may be, for example, a button. In some embodiments, thepreliminary data may be in response to the HMD receiving a voice commandfrom the user. For example, a microphone of the HMD may detect a usersay “Camera” or “Let's take a picture”, and generate the preliminarydata. Other examples are also possible.

b. Initiating a Camera

As shown by block 404, the method 400 may involve initiating a camera ofthe HMD (e.g., the image capture device 178) in response to the receiptof the preliminary data. Initiating the camera may involve initiating animage-capture preparation process that causes the camera to be ready tocapture an image or a video if the user does, in fact, engage in furtherimage-capture steps (described below).

In a further example embodiment, the image-capture preparation processmay involve various functions or combinations of functions. As examples,an image-capture preparation process may involve: (a) powering up acamera sensor, (b) powering up a camera chipset, (c) powering upinternal cores of the HMD that run camera driver software, (d)pre-allocating memory buffers for the cameras functions, (e)establishing a connection (e.g., an OMX connection) between a mainuser-space core (such as that of the HMD's operating system) and thecamera controller cores, and/or (f) setting default imaging parametersfor the camera.

In other embodiments, referring now to FIG. 6A, initiating the cameramay involve initiating a camera preview process to acquire a stream ofimage frames from the camera. For example, as shown, a stream of imageframes 610 may depict a scene as viewed by a wearer of the HMD. In someinstances, the image frames may then be used to carry out anauto-exposure process, an auto-focus process, and/or an automaticwhite-balancing process, among other possibilities. Further, such imageframes might be used to preview the scene in a viewfinder and/or displayof the HMD, e.g., the single display 180.

In some embodiments, in response to the receipt of the preliminary data,the method 400 may further involve causing the control system to operatein a camera mode. That is, before receiving the preliminary data, thecontrol system may be operating in a first mode. In response toreceiving the preliminary data, the control system may operate in asecond mode (e.g., the camera mode) such that the control system mayperform different operations in response to receiving certain data fromthe first and second input interfaces. For example, while operating inthe camera mode, the control system may receive data from the firstinput interface or the second input interface that corresponds to thesame or similar input action as the preliminary input action, but thecontrol system may perform an operation different than initiating thecamera.

c. Receiving Input Data Corresponding to a First Input Action

At block 406, the method 400 may involve receiving first input data fromthe first input interface that corresponds to a first input action. Insome embodiments, as discussed above, the method 400 may begin at block406.

In either case, the first input action may take the form of any suitableaction at the first input interface, which may depend on the type of thefirst input interface. In one example, where the first input interfaceis a slider, the first input action may involve sliding the slidertowards the anterior surface 314 or sliding the slider towards theposterior surface 316. In another example, where the first inputinterface is a rocker, the first input action may involve rocking therocker towards the anterior surface 314 or rocking the rocker towardsthe posterior surface 316. Other examples are also possible. In responseto the first input action, the first input interface may be configuredto transmit the first input data to the control system

In example embodiments, the first input action may be a finger gestureat the first input interface (e.g., any of the finger gestures discussedabove). With reference to FIG. 5B, which illustrates an example use ofthe housing configuration 300 at a second point in time, such a fingergesture may be performed by the thumb 510 (or other finger) of theuser's hand 500. As indicated by the motion arrow adjacent to the thumb510, the thumb 510 may perform the finger gesture by sliding along thefirst input interface 330. In particular, as shown, the first inputinterface 330 may receive the finger gesture (here, a forward fingerrub) by first detecting a touch input 516 and then detecting the thumb510 sliding forward, as indicated by the motion arrow adjacent to thefinger input 516. The first input interface 330 may be configured togenerate data in response to detecting the finger gesture and transmitthe data to the control system of the HMD.

In other embodiments, the first input action may be a prolonged touch atthe first input interface. For example, the first input action may bethe touch input 516 held at the first input interface 330 for apredefined amount of time, e.g., 2 or more seconds. The first inputinterface 330 may detect the prolonged touch and transmit the firstinput data to the control system accordingly.

In other embodiments, the control system may be in the camera mode.While in the camera mode, the first input action may be the same as orsimilar to the preliminary input action as described with reference toblock 400, in addition to the above example first input actions.

d. Perform First Camera Operation

As shown by block 408, the method 400 may involve, responsive to receiptof the first input data, causing the camera of the device to perform afirst camera operation in accordance with the first input action. Insome embodiments, the first camera operation may involve zooming thecamera, adjusting exposure levels, adjusting focus depth, adjustingwhite balance settings, switching between filters, switching betweenstabilization modes, or navigating camera settings, among other cameraoperations.

In some embodiments, the camera may, for example, zoom in or zoom outdepending on the first input action. For example, the control system mayreceive the first input data that indicates a forward finger roll, aforward finger rub, a backward finger swipe, a prolonged finger touch,or a finger pinch, among other examples and cause the camera to zoom in.Further, the control system may receive the first input data thatindicates a backward finger roll, a backward finger rub, a forwardfinger swipe, or an outward finger pinch and cause the camera to zoomout. Alternatively, the control system may be configured to perform theopposite zooming operation in response to the described first inputactions. Other examples are also possible.

In other embodiments, the camera may increase or decrease exposurelevels, focus depth, or white balance settings according to the firstinput action. For example, a forward finger gesture may cause anincrease, while a backward finger gesture may cause a decrease, amongother examples. In some embodiments, the camera may cycle throughfilters, stabilization modes, or camera settings according to the firstinput action. For example, a forward finger gesture may cause the camerato cycle in one direction, while a backward finger gesture may cause thecamera to cycle in a different direction. Other example first cameraoperations are also possible.

In some embodiments, causing the camera to perform the first cameraoperation may involve adjusting the camera preview such that theacquired stream of image frames is modified. For example, referring nowto FIG. 6B, a stream of image frames 620 may be a zoomed in version ofthe scene depicted in the stream of image frames 610, in accordance withthe first input action (a forward finger rub). Further, such modifiedimage frames might be used to preview the zoomed in scene in theviewfinder and/or display of the HMD

In other embodiments, causing the camera to perform the first cameraoperation may be further in response to the control system receivingdata from the second input interface. That is, in order to perform thefirst camera operation using the first input interface 330, a user mayalso need to provide input at the second input interface 320.

e. Receiving Input Data Corresponding to the Second Input Action

At block 410, the method 400 may involve receiving second input datafrom the second input interface that corresponds to a second inputaction. The second input action may take the form of any suitable actionat the second input interface, which may depend on the type of thesecond input interface.

For example, the second input action may involve a click or depressionof a button, a touch of a touch sensor, a finger hover above a touchsensor, a rocking of a rocker, a turn of a dial, a slide of a slider, aflip of switch, or a spin of a wheel. In other instances, where thesecond input interface is a touch sensor, the second input action mayinvolve a user pressing a finger to the touch sensor and holding thefinger for a predefined period of time, or the second input action mayinvolve one of the finger gestures as described above. Other examplesecond input actions are also possible. In some embodiments, the secondinput action may be the same as or similar to the preliminary inputaction. In response to the second input action, the second inputinterface may be configured to transmit the second input data to thecontrol system.

In one example, the second input action may be a touch input at thesecond input interface. With reference to FIG. 5C, which illustrates anexample use of the housing configuration 300 at a third point in time,such a touch input may be performed by the pointer finger 520 (or anyother finger) of the user's hand 500. As indicated by the motion arrowadjacent to the pointer finger 520, the pointer finger 520 may perform atouch input 525 by touching the second input interface 320. The touchinput 525 may be a prolonged touch (e.g., for 2 or more seconds) or abrief touch at the second input interface 320. The second inputinterface 320 may be configured to generate the second input data inresponse to detecting the touch input 525 and transmit the second inputdata to the control system of the HMD.

In some embodiments, the second input data may correspond to acombination of the first input action and the second input action. Forexample, as shown in FIG. 5C, the first input interface 330 may transmitdata corresponding to touch input 517 (which may be where the forwardfinger rub stopped), and the second input interface 320 may transmitdata corresponding to the touch input 525. The control system mayinterpret this combination of data as the second input data. Otherexamples are also possible.

Thus, as illustrated in FIGS. 5A-5C, the housing configuration 300 mayprovide the user with an ergonomic configuration of input interfacesthat helps provide a natural and intuitive manner to perform multi-touchcamera operations with the HMD. As shown, the ergonomic configurationmay allow the user to perform a first camera operation with the thumb510 at the first input interface 330, while leaving other fingersavailable to perform a second camera operation (e.g., take a picture orrecord a video) with the second input interface 320 once the thumb 510has satisfactorily performed the first camera operation.

In another embodiment, the housing configuration 350 of FIG. 3B may alsoprovide a natural way to perform multi-touch camera operations with theHMD. The user may perform a first camera operation with the pointerfinger 520 at the first input interface 330 located on the superiorsurface 310, and when desired, the user may conveniently use the thumb510 at the second input interface 320 located on the inferior surface312 to perform a second camera operation, e.g., capture an image orrecord a video. The described housing configurations may provide theuser with the natural feeling of squeezing the housing while operatingthe camera, which may provide the user with greater control and/or morefine-tuned control of the HMD.

f. Perform Second Camera Operation

As shown by block 412, the method 400 may involve, responsive to thereceipt of the second input data, causing the camera to perform a secondcamera operation that is different from the first camera operation. Insome embodiments, the second camera operation may involve capturingimage data in accordance with the first input action. For example, thecamera may capture a zoomed in/out image, a low/high level exposureimage, a low/high depth focused image, or an image with a particularfilter, among other examples. Referring to FIG. 6C, the camera maycapture image data 630 that corresponds to the scene depicted in thezoomed in image frame 620. In example embodiments, the second cameraoperation may involve capturing video data.

In other embodiments, the second camera operation may involve selectinga camera function in accordance with the first input action. Forexample, the camera may cycle to a desired function of the camera as aresult of the first input action, and the second camera operation mayinvolve selecting the desired function and/or initiating an aspect of animage-capture preparation process as indicated by the desired function.Other examples are also possible.

In some embodiments, the second camera operation or the result of thesecond camera operation may be displayed to the user via the viewfinderand/or display of the HMD. For example, where the second cameraoperation involves capturing image data, the captured image data may bedisplayed to the user of the HMD.

It should be understood that any combination of inputs at the first andsecond input interfaces may result in the camera performing multi-touchoperations. Further, the inputs may be any combination of input types.It should be further understood that the blocks of method 400 may beperformed in different orders and ultimately cause the camera to performa first and a second camera operation.

In other embodiments, the second camera operation may involve capturingvideo data. In such an embodiment, while recording a video, the controlsystem may be configured to modify a video recording setting (e.g., zoomduring recording) in response to another input that is the same orsimilar to the first input action. Other examples are also possible.

In a further aspect of an example method (not shown), the user mayprovide a preliminary input action at the second input interface 320,which may in turn initiate the camera. For example, the user may touchthe second input interface 320 with the user's pointer finger 520 andhold the pointer finger 520 on the second input interface 320. The usermay next provide a first input action at the first input interface 330,which may cause the camera to perform a first camera operation, e.g.,zoom out. For example, the user may perform a backward finger roll onthe first input interface 330 with the user's thumb 510. The user maythen remove the thumb 510 from the first input interface 330. As aspecific example, the user may remove the user's thumb 510 once thecamera has zoomed out to the user's satisfaction. Lastly, the user mayremove the pointer finger 520 from the second input interface 320thereby causing the camera to perform a second camera operation, e.g.,capture zoomed out image data according to the backward finger roll.Other examples are certainly possible.

It should further be understood that inputs at the first and secondinput interfaces could cause the control system to perform othermulti-step operations in addition to the above camera example. Forexample, the method 400 or portions of the method 400 may be utilized toperform controlling an audio source or adjusting the volume of a speakerof the HMD (e.g., the speaker 125 or the BCT 186).

In one such embodiment, the control system may receive preliminary datafrom either the first input interface or the second input interface thatcorresponds to a preliminary input action. For example, the user maytouch the second input interface 320 with the user's pointer finger 520and hold the pointer finger 520 on the second input interface 320.

In response to the receipt of the preliminary data, the control systemmay initiate volume control. For example, the control system may detecta current volume level of a speaker of the HMD and/or the control systemmay output to a display of the HMD a volume control indicator.

The control system may then receive first input action data thatcorresponds to a combination of a first input action at the first inputinterface and a second input action at the second input interface. Thefirst input action may be a finger gesture or any of the input actionsdescribed above. Similarly, the second input action may be any of theinput actions described above or may be the same as the preliminaryinput action. For example, while the user is still touching the secondinput interface 320 with the user's pointer finger 520, the user mayprovide a finger gesture with the user's thumb 510 at the first inputinterface 330.

In response to the receipt of the first input data, the control systemmay perform a volume operation according to the first input action. Forexample, the control system may increase or decrease the volume level.Further, the control system may also display the change in the volumelevel at the displayed volume control indicator.

The control system may then receive third input action datacorresponding to a third input action at the first input interface orthe second input interface. In some embodiments, the third input actiondata may correspond to a combination of input actions at the first andsecond input interfaces. The third input action may be any of the inputactions described above. In one example, the third input action may bethe user removing the thumb 510 from the first input interface 330,among other input actions. In response to the receipt of the third inputaction data, the control system may perform a second volume operationthat is different from the first volume operation, e.g., output audio atthe speaker according to the first input action.

Further, the control system may receive a fourth input actioncorresponding to a fourth input action at the first input interface orthe second input interface. In some embodiments, the fourth input actiondata may correspond to a combination of input actions at the first andsecond input interfaces. In some embodiments, the fourth input actionmay be the same as or similar to the third input action. In one example,the third input action may be the user removing the pointer finger 520from the second input interface 320, among other input actions. Inresponse to the receipt of the fourth input action data, the controlsystem may perform a third volume operation that is different from thefirst and second volume operations, e.g., no longer display the volumecontrol indicator. Other example multi-step operations may be performedutilizing the ergonomic configuration of the first and second inputinterfaces described herein.

IV. CONCLUSION

It should be understood that the examples described with reference to anHMD are not limited to an HMD. It is contemplated that the examplemethods and systems described with reference to an HMD may beimplemented on other types of computing devices, such as other types ofwearable devices, mobile phones, tablet computers, and/or laptopcomputers, for instance.

More generally, while various aspects and embodiments have beendisclosed herein, other aspects and embodiments will be apparent tothose skilled in the art. The various aspects and embodiments disclosedherein are for purposes of illustration and are not intended to belimiting, with the true scope and spirit being indicated by thefollowing claims.

We claim:
 1. A wearable device comprising: a housing; a first inputinterface arranged on either a superior surface or an inferior surfaceof the housing and configured to receive a first plurality of gesturesperformed by at least a thumb of a hand; a second input interfacearranged on a surface of the housing that is opposite to the first inputinterface and configured to receive a second plurality of gesturesperformed by one or more input devices; and a control system configuredto: receive first input data from the first input interface, wherein thefirst input data corresponds to a first input action that is one or moreof the first plurality of gestures, and responsive to the receipt of thefirst input data, cause the device to perform a first operation inaccordance with the first input action; and receive second input datafrom the second input interface, wherein the second input datacorresponds to one or more second input actions that are one or more ofthe second plurality of gestures, and responsive to the receipt of thesecond input data, cause the device to perform a second operation thatis different from the first operation.
 2. The device of claim 1, whereinthe first input interface is arranged on the superior surface of thehousing, and wherein the second input interface is arranged on theinferior surface of the housing.
 3. The device of claim 1, wherein thefirst input interface is arranged on the inferior surface of thehousing, and wherein the second input interface is arranged on thesuperior surface of the housing.
 4. The device of claim 1, wherein thefirst input interface is one of a button, a touch sensor, a rocker, adial, a slider, and a multi-state sensor.
 5. The device of claim 1,wherein the second input interface is one of a button, a touch sensor, arocker, a dial, a slider, and a multi-state sensor.
 6. The device ofclaim 1, wherein the first operation comprises adjusting a volume levelof a speaker of the wearable device.
 7. The device of claim 1, whereinthe control system is further configured to: operate in a first mode;and receive preliminary data that corresponds to a preliminary inputaction, and responsive to the receipt of the preliminary data, cause thecontrol system to operate in a second mode.
 8. The device of claim 1,wherein the first plurality of gestures is one of a finger roll, afinger rub, a finger swipe, a finger pinch, and a prolonged touch. 9.The device of claim 1, wherein the input devices comprise one or morefingers of the hand.
 10. A method comprising: receiving first input datafrom a first input interface that corresponds to a first input actionthat is one or more of a first plurality of gestures, wherein the firstinput interface is arranged on either a superior surface or an inferiorsurface of a housing of a wearable device, wherein the first inputinterface is configured to receive the first plurality of gesturesperformed by at least a thumb of a hand; responsive to the receipt ofthe first input data, causing the device to perform a first operation inaccordance with the first input action; receiving second input data froma second input interface that corresponds to a second input action thatis one or more of a second plurality of gestures, wherein the secondinput interface is arranged on a surface of the housing that is oppositeto the first input interface, wherein the second input interface isconfigured to receive the second plurality of gestures performed by oneor more input devices; and responsive to the receipt of the second inputdata, causing the device to perform a second operation that is differentfrom the first operation.
 11. The method of claim 10, wherein the firstinput interface is arranged on the inferior surface of the housing, andwherein the second input interface is arranged on the superior surfaceof the housing.
 12. The method of claim 10, wherein the first inputinterface is arranged on the superior surface of the housing, andwherein the second input interface is arranged on the inferior surfaceof the housing.
 13. The method of claim 10, wherein the first operationcomprises adjusting a volume level of a speaker of the wearable device.14. The method of claim 10, wherein the first plurality of gestures isone of a finger roll, a finger rub, a finger swipe, a finger pinch, anda prolonged touch.
 15. The method of claim 10, wherein the secondplurality of gestures is one of a finger roll, a finger rub, a fingerswipe, and a prolonged touch.
 16. A non-transitory computer readablememory having stored therein instructions executable by a computingdevice to cause the computing device to perform functions comprising:receiving first input data from a first input interface that correspondsto a first input action that is one or more of a first plurality ofgestures, wherein the first input interface is arranged on either asuperior surface or an inferior surface of a housing of a wearabledevice, wherein the first input interface is configured to receive thefirst plurality of gestures performed by at least a thumb of a hand;responsive to the receipt of the first input data, causing the deviceperform a first operation in accordance with the first input action;receiving second input data from a second input interface thatcorresponds to a second input action that is one or more of a secondplurality of gestures, wherein the second input interface is arranged ona surface of the housing that is opposite to the first input interface,wherein the second input interface is configured to receive the secondplurality of gestures performed by one or more input devices; andresponsive to the receipt of the second input data, causing the deviceto perform a second operation that is different from the firstoperation.
 17. The non-transitory computer readable memory of claim 16,wherein the first input interface is arranged on the inferior surface ofthe housing, and wherein the second input interface is arranged on thesuperior surface of the housing.
 18. The non-transitory computerreadable memory of claim 16, wherein the first input interface isarranged on the superior surface of the housing, and wherein the secondinput interface is arranged on the inferior surface of the housing. 19.The non-transitory computer readable memory of claim 16, wherein thefirst plurality of gestures is one of a finger roll, a finger rub, afinger swipe, a finger pinch, and a prolonged touch.
 20. Thenon-transitory computer readable memory of claim 16, wherein the inputdevices comprise one or more fingers of the hand.